Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0130b92d3b3cfa5b9d5083791c7f862bcd2a5f50f912babee3bf1ad14d839bd5

Tx prefix hash: b2b6e3f2ecf28531609598f929ddf20c7a41bf9d745e6ffd8fad15303e74a4fa
Tx public key: 96f296dd61f379875dfc499bbacf70566b05fed7c15b5d08c3e29759f810c2ac
Timestamp: 1745840175 Timestamp [UCT]: 2025-04-28 11:36:15 Age [y:d:h:m:s]: 00:008:21:43:05
Block: 1271272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6364 RingCT/type: yes/0
Extra: 0196f296dd61f379875dfc499bbacf70566b05fed7c15b5d08c3e29759f810c2ac0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28a9631cfc6a7ba8b507f912730f4370a9236ed76a0ad4ba5d5c505e0e5dfbae 0.600000000000 1758529 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": 1271282, "vin": [ { "gen": { "height": 1271272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28a9631cfc6a7ba8b507f912730f4370a9236ed76a0ad4ba5d5c505e0e5dfbae" } } ], "extra": [ 1, 150, 242, 150, 221, 97, 243, 121, 135, 93, 252, 73, 155, 186, 207, 112, 86, 107, 5, 254, 215, 193, 91, 93, 8, 195, 226, 151, 89, 248, 16, 194, 172, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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