Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 910b408695d0266d4eb6cc9f123e4352bf7ada19e0e4ed399f1e2eace01f23c2

Tx prefix hash: db093cd44cdc8821862f9970830ed163089a3412b792cb187ffe1b48af062bd9
Tx public key: 29ebd4b4ff4789b1777e953804e9d0182a7b918212401ec9619ab80a7eb8e7d6
Timestamp: 1584920247 Timestamp [UCT]: 2020-03-22 23:37:27 Age [y:d:h:m:s]: 04:183:05:00:25
Block: 86763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1027938 RingCT/type: yes/0
Extra: 0129ebd4b4ff4789b1777e953804e9d0182a7b918212401ec9619ab80a7eb8e7d602110000000a4943cd9f000000000000000000

1 output(s) for total of 316.605856446000 dcy

stealth address amount amount idx
00: 5469bde25929aaf19dbd7a9d4aa7c0b0819b3651b75529237cde0af04c8ac152 316.605856446000 156567 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": 86773, "vin": [ { "gen": { "height": 86763 } } ], "vout": [ { "amount": 316605856446, "target": { "key": "5469bde25929aaf19dbd7a9d4aa7c0b0819b3651b75529237cde0af04c8ac152" } } ], "extra": [ 1, 41, 235, 212, 180, 255, 71, 137, 177, 119, 126, 149, 56, 4, 233, 208, 24, 42, 123, 145, 130, 18, 64, 30, 201, 97, 154, 184, 10, 126, 184, 231, 214, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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