Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 262a5cfc76f4cb32a29941b433a7c46c3f4262a175fff40ef9b53db4ab9414d3

Tx prefix hash: bac2aab801026939acf1b9825e848e8c4b53f7c43bd8fc6cbababf80cc9ac1cf
Tx public key: 878a4eb80ad2a12a5250d4e638cdb9bf95469049a8d4b7313a81af2ea36baa29
Timestamp: 1740146382 Timestamp [UCT]: 2025-02-21 13:59:42 Age [y:d:h:m:s]: 00:285:12:48:19
Block: 1224098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201874 RingCT/type: yes/0
Extra: 01878a4eb80ad2a12a5250d4e638cdb9bf95469049a8d4b7313a81af2ea36baa290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb4de13b2e2a8443411afebc2dadaee3dd1b4b5a594a311811e7df4a106371a7 0.600000000000 1710955 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1224108, "vin": [ { "gen": { "height": 1224098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb4de13b2e2a8443411afebc2dadaee3dd1b4b5a594a311811e7df4a106371a7" } } ], "extra": [ 1, 135, 138, 78, 184, 10, 210, 161, 42, 82, 80, 212, 230, 56, 205, 185, 191, 149, 70, 144, 73, 168, 212, 183, 49, 58, 129, 175, 46, 163, 107, 170, 41, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8