Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5bce2d143d9fc5f85da0581be4e6dbf7ca595343fb3c005db65f9c9df52829b

Tx prefix hash: fdb5881c483f4fd1f5dde399d695cb4e3cac82903a01e14e46c3b8e89ca5960e
Tx public key: af649aa2133b898408871b2bded6e697f6b370b82139f88ab6b35dbb75f6e47f
Timestamp: 1736464835 Timestamp [UCT]: 2025-01-09 23:20:35 Age [y:d:h:m:s]: 00:148:04:04:46
Block: 1193926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105712 RingCT/type: yes/0
Extra: 01af649aa2133b898408871b2bded6e697f6b370b82139f88ab6b35dbb75f6e47f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d8e0368f5dca35536edeb530d395954b4c897959cffd696a93affe63ef07815 0.600000000000 1680491 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": 1193936, "vin": [ { "gen": { "height": 1193926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d8e0368f5dca35536edeb530d395954b4c897959cffd696a93affe63ef07815" } } ], "extra": [ 1, 175, 100, 154, 162, 19, 59, 137, 132, 8, 135, 27, 43, 222, 214, 230, 151, 246, 179, 112, 184, 33, 57, 248, 138, 182, 179, 93, 187, 117, 246, 228, 127, 2, 17, 0, 0, 0, 1, 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