Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c46d9b61de93b55ed97c2735f1f2a4149a04168d1a1125256e7be64daa310b4

Tx prefix hash: 2552ce4a9ab2de0775dcf335d9c98e8480b0b2540eb3b1d270e5621b6ee2ad21
Tx public key: 70367b544f0e7eaf17eef9185fdc5da63d716f90ec91403da86acec9f72d2810
Timestamp: 1763412672 Timestamp [UCT]: 2025-11-17 20:51:12 Age [y:d:h:m:s]: 00:010:11:34:43
Block: 1414340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7500 RingCT/type: yes/0
Extra: 0170367b544f0e7eaf17eef9185fdc5da63d716f90ec91403da86acec9f72d2810021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65306e8473aa8edba8fb970b0c1cf1d91d417a316e4983bed744dc493ea79ee1 0.600000000000 1902827 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": 1414350, "vin": [ { "gen": { "height": 1414340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65306e8473aa8edba8fb970b0c1cf1d91d417a316e4983bed744dc493ea79ee1" } } ], "extra": [ 1, 112, 54, 123, 84, 79, 14, 126, 175, 23, 238, 249, 24, 95, 220, 93, 166, 61, 113, 111, 144, 236, 145, 64, 61, 168, 106, 206, 201, 247, 45, 40, 16, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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