Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2765a4b40fc247e5d814a5606eb1eef22cb8efcff589be2b41fa6e25d1d4ce0d

Tx prefix hash: 144913a764c513da312fb08fcf11fbaa9bb4f739ef73dd58b6002bcf84d2848b
Tx public key: f6e430a8424ce9509b8a06a386f763d4a4e3023486e7b4f3068efbf430c39411
Timestamp: 1749441206 Timestamp [UCT]: 2025-06-09 03:53:26 Age [y:d:h:m:s]: 00:161:20:47:55
Block: 1301093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113366 RingCT/type: yes/0
Extra: 01f6e430a8424ce9509b8a06a386f763d4a4e3023486e7b4f3068efbf430c3941102110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ba030e1ddb93f59f604b3e4bdf5782ab68b2956623ffa98f097a9208f520e2 0.600000000000 1788646 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": 1301103, "vin": [ { "gen": { "height": 1301093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ba030e1ddb93f59f604b3e4bdf5782ab68b2956623ffa98f097a9208f520e2" } } ], "extra": [ 1, 246, 228, 48, 168, 66, 76, 233, 80, 155, 138, 6, 163, 134, 247, 99, 212, 164, 227, 2, 52, 134, 231, 180, 243, 6, 142, 251, 244, 48, 195, 148, 17, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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