Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bb726df16ad9e69895ace6560971005f5d32dc7abc1378d525218e3080f4e91

Tx prefix hash: 026788124ed941c4dcf74ce2dd9f2952c881408f1328feafc2e01dbd0b356bf4
Tx public key: d2013b8fe0e525fb6623e74660dcb24a6876f67d84a0e5d4eef1a6e0ba8ca383
Timestamp: 1694083107 Timestamp [UCT]: 2023-09-07 10:38:27 Age [y:d:h:m:s]: 01:138:13:30:35
Block: 842883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360315 RingCT/type: yes/0
Extra: 01d2013b8fe0e525fb6623e74660dcb24a6876f67d84a0e5d4eef1a6e0ba8ca383021100000001faf35c9c000000000000000000

1 output(s) for total of 0.988960147000 dcy

stealth address amount amount idx
00: 641d620d5d449f81f01edc59237050ed34335e4dc0c301e717a6c62b846d976c 0.988960147000 1296051 of 0

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": 842893, "vin": [ { "gen": { "height": 842883 } } ], "vout": [ { "amount": 988960147, "target": { "key": "641d620d5d449f81f01edc59237050ed34335e4dc0c301e717a6c62b846d976c" } } ], "extra": [ 1, 210, 1, 59, 143, 224, 229, 37, 251, 102, 35, 231, 70, 96, 220, 178, 74, 104, 118, 246, 125, 132, 160, 229, 212, 238, 241, 166, 224, 186, 140, 163, 131, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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