Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a54f3353d55f31e2909d87fde3b1b4eb114f12cc18779e72d0e839a7a6e3e072

Tx prefix hash: c48616dbfe6ef7743fe293ec781f8d1d8b491d3ed3db0e08602f79c3957ab549
Tx public key: 80273ee78de0b81e9e08f731540c721cd71efed0064e15f2469b99b516a7e55b
Timestamp: 1763404669 Timestamp [UCT]: 2025-11-17 18:37:49 Age [y:d:h:m:s]: 00:036:08:24:42
Block: 1414276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26016 RingCT/type: yes/0
Extra: 0180273ee78de0b81e9e08f731540c721cd71efed0064e15f2469b99b516a7e55b021100000002da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba9caf3a8b85dee00d12e2a86840411a328636d71680d067294c4a19aae0855c 0.600000000000 1902763 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": 1414286, "vin": [ { "gen": { "height": 1414276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba9caf3a8b85dee00d12e2a86840411a328636d71680d067294c4a19aae0855c" } } ], "extra": [ 1, 128, 39, 62, 231, 141, 224, 184, 30, 158, 8, 247, 49, 84, 12, 114, 28, 215, 30, 254, 208, 6, 78, 21, 242, 70, 155, 153, 181, 22, 167, 229, 91, 2, 17, 0, 0, 0, 2, 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