Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95b6aad563a2340e9aa71dd308e105cd50ff1fb1d3936246782fcbaa5f05824

Tx prefix hash: f797109dd4b375ac1edd0d042f5ab3384f7c55b879afde3971732515cab942ce
Tx public key: 34f9a718bfd4534b2b7977e94c4644228ba4275e7ed83c41f51a2732c4c1084e
Timestamp: 1737258963 Timestamp [UCT]: 2025-01-19 03:56:03 Age [y:d:h:m:s]: 00:057:08:53:27
Block: 1200461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40822 RingCT/type: yes/0
Extra: 0134f9a718bfd4534b2b7977e94c4644228ba4275e7ed83c41f51a2732c4c1084e021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b47d01c44d5b4f71bd6abc62d0ed9f24c08b62e1aec9f8f663ff77a2468f5a1 0.600000000000 1687104 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": 1200471, "vin": [ { "gen": { "height": 1200461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b47d01c44d5b4f71bd6abc62d0ed9f24c08b62e1aec9f8f663ff77a2468f5a1" } } ], "extra": [ 1, 52, 249, 167, 24, 191, 212, 83, 75, 43, 121, 119, 233, 76, 70, 68, 34, 139, 164, 39, 94, 126, 216, 60, 65, 245, 26, 39, 50, 196, 193, 8, 78, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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