Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec28dd63f1f05344a179ee401d4caec8f79ff2698fbdff3e4d278e12b1eb1de

Tx prefix hash: f9f03b3d7c6a0b5dc9d92c4fa2a2d9a60b66fabb4686440b963ea802f53a692a
Tx public key: 5b56f8b1bfaa3b5a87e4ab96ba3abdf9d71e43dfdd3e6bb39fb427ff31c4b1b7
Timestamp: 1745254593 Timestamp [UCT]: 2025-04-21 16:56:33 Age [y:d:h:m:s]: 00:259:03:20:32
Block: 1266412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183014 RingCT/type: yes/0
Extra: 015b56f8b1bfaa3b5a87e4ab96ba3abdf9d71e43dfdd3e6bb39fb427ff31c4b1b702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba08b00425b939939f1713e4b099105a20805d593c95e5f84fb362a84d3638a5 0.600000000000 1753633 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": 1266422, "vin": [ { "gen": { "height": 1266412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba08b00425b939939f1713e4b099105a20805d593c95e5f84fb362a84d3638a5" } } ], "extra": [ 1, 91, 86, 248, 177, 191, 170, 59, 90, 135, 228, 171, 150, 186, 58, 189, 249, 215, 30, 67, 223, 221, 62, 107, 179, 159, 180, 39, 255, 49, 196, 177, 183, 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