Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc37354d34bb000cd4b452fafbcf62cb3528a6e1b1e7c6ab91a2f1b228a962f

Tx prefix hash: 42361f582ef603dda49aa56f59fd44d2e13dede5f0d2e3900f9c9eb67b3b06a8
Tx public key: 2203f729bdfc1f93969c56ef13125c301c83e72620dcc0aa49ef01e24d1470fd
Timestamp: 1745782283 Timestamp [UCT]: 2025-04-27 19:31:23 Age [y:d:h:m:s]: 00:207:16:31:46
Block: 1270790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146144 RingCT/type: yes/0
Extra: 012203f729bdfc1f93969c56ef13125c301c83e72620dcc0aa49ef01e24d1470fd02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc076dbea47b7ee0d8c29b0fad1f8563a7bc37765d7721620c3dad56cf52ca50 0.600000000000 1758035 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": 1270800, "vin": [ { "gen": { "height": 1270790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc076dbea47b7ee0d8c29b0fad1f8563a7bc37765d7721620c3dad56cf52ca50" } } ], "extra": [ 1, 34, 3, 247, 41, 189, 252, 31, 147, 150, 156, 86, 239, 19, 18, 92, 48, 28, 131, 231, 38, 32, 220, 192, 170, 73, 239, 1, 226, 77, 20, 112, 253, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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