Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b676275fcd00cc324e5e74a206446277979b41d9d7e31b181d392515df8de1

Tx prefix hash: c8d57baab3da87124af282cbef9aab52d5b3bc8e53f563fb1eb5d4dbfd9f672a
Tx public key: dd4fe693d7d1a4f7922516f6a067efac08345afa7fe577212a10dbf30f1cdfaa
Timestamp: 1602855077 Timestamp [UCT]: 2020-10-16 13:31:17 Age [y:d:h:m:s]: 05:067:03:23:52
Block: 141690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1296879 RingCT/type: yes/0
Extra: 01dd4fe693d7d1a4f7922516f6a067efac08345afa7fe577212a10dbf30f1cdfaa02110000003cf4b4cc44000000000000000000

1 output(s) for total of 208.220226502000 dcy

stealth address amount amount idx
00: 44fc5c742cccd33af10ef3e653cc70a76959ab4060ff13a682fda5c842ec1a6e 208.220226502000 235326 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": 141700, "vin": [ { "gen": { "height": 141690 } } ], "vout": [ { "amount": 208220226502, "target": { "key": "44fc5c742cccd33af10ef3e653cc70a76959ab4060ff13a682fda5c842ec1a6e" } } ], "extra": [ 1, 221, 79, 230, 147, 215, 209, 164, 247, 146, 37, 22, 246, 160, 103, 239, 172, 8, 52, 90, 250, 127, 229, 119, 33, 42, 16, 219, 243, 15, 28, 223, 170, 2, 17, 0, 0, 0, 60, 244, 180, 204, 68, 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