Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d148121a05de573af47924bda3f67d116b37a67a82f78fe741da78fb88e38f88

Tx prefix hash: f150361a148411446e3a20f2a6f6945d465837db7552d7760c7885b64c2e983f
Tx public key: b2b2d4b2ca736a0ac00f0372904df524b446c559a7dd8ee02e9e7dd3003b1f8d
Timestamp: 1746190097 Timestamp [UCT]: 2025-05-02 12:48:17 Age [y:d:h:m:s]: 00:203:04:30:30
Block: 1274158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142932 RingCT/type: yes/0
Extra: 01b2b2d4b2ca736a0ac00f0372904df524b446c559a7dd8ee02e9e7dd3003b1f8d0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a6e28037e23d3dcadeac1af7982bf99d85837232b44b458da75525cb5391d71 0.600000000000 1761449 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": 1274168, "vin": [ { "gen": { "height": 1274158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a6e28037e23d3dcadeac1af7982bf99d85837232b44b458da75525cb5391d71" } } ], "extra": [ 1, 178, 178, 212, 178, 202, 115, 106, 10, 192, 15, 3, 114, 144, 77, 245, 36, 180, 70, 197, 89, 167, 221, 142, 224, 46, 158, 125, 211, 0, 59, 31, 141, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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