Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d81bcc4c2170c94c98269c7a2d6f8539b987f7127a7e5c4d11b4c2240c7f7cf9

Tx prefix hash: fd810dd77f603f2aa42cbd11631d6f07688cd02eab2cec7e0b8a0fb7b5576a8f
Tx public key: 017b3f788d422859ba090a231f6159e0f772be8cfc623b762373b7e370560fbd
Timestamp: 1577222880 Timestamp [UCT]: 2019-12-24 21:28:00 Age [y:d:h:m:s]: 05:048:05:31:12
Block: 31033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184192 RingCT/type: yes/0
Extra: 01017b3f788d422859ba090a231f6159e0f772be8cfc623b762373b7e370560fbd021100000065ac34bf9e000000000000000000

1 output(s) for total of 484.368229541000 dcy

stealth address amount amount idx
00: e7dbe1732dfd4f79d4d7a49d15d3258aefdad766bf3716f9f6f237779a9b9c08 484.368229541000 51267 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": 31043, "vin": [ { "gen": { "height": 31033 } } ], "vout": [ { "amount": 484368229541, "target": { "key": "e7dbe1732dfd4f79d4d7a49d15d3258aefdad766bf3716f9f6f237779a9b9c08" } } ], "extra": [ 1, 1, 123, 63, 120, 141, 66, 40, 89, 186, 9, 10, 35, 31, 97, 89, 224, 247, 114, 190, 140, 252, 98, 59, 118, 35, 115, 183, 227, 112, 86, 15, 189, 2, 17, 0, 0, 0, 101, 172, 52, 191, 158, 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