Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b273b4a9701e1df1def444ec3806988adf47042433db4e1b13a861d1e113b9

Tx prefix hash: be9a76396b36910627861cf83f15062866f77f8f4b6263a8a8bd11fe5b8656b0
Tx public key: 5b9932dd576b429533dd057d1e48100d4ed776f1d01f4de64074731173a82752
Timestamp: 1617102398 Timestamp [UCT]: 2021-03-30 11:06:38 Age [y:d:h:m:s]: 03:285:19:11:18
Block: 229656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 963753 RingCT/type: yes/0
Extra: 015b9932dd576b429533dd057d1e48100d4ed776f1d01f4de64074731173a8275202110000004b7071732b000000000000000000

1 output(s) for total of 106.431439454000 dcy

stealth address amount amount idx
00: 6112c431e29b4ecee3c3c2307a6cbbbf0d83c2eee26f9ff8c80e8d56d2f8719d 106.431439454000 476594 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": 229666, "vin": [ { "gen": { "height": 229656 } } ], "vout": [ { "amount": 106431439454, "target": { "key": "6112c431e29b4ecee3c3c2307a6cbbbf0d83c2eee26f9ff8c80e8d56d2f8719d" } } ], "extra": [ 1, 91, 153, 50, 221, 87, 107, 66, 149, 51, 221, 5, 125, 30, 72, 16, 13, 78, 215, 118, 241, 208, 31, 77, 230, 64, 116, 115, 17, 115, 168, 39, 82, 2, 17, 0, 0, 0, 75, 112, 113, 115, 43, 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