Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c034ecbaea1e09e15d846a3cfef0f7857892b7ce57fa29f3cdca246dec744f4

Tx prefix hash: 9439d969921b510061d361b2c63a94635d3310689f4d2df2ff3d599d8017cdc2
Tx public key: 775c2e8d3e26151ae1e49c55434653aabed7582edf87cb4e54288facf4d4cc6e
Timestamp: 1723917397 Timestamp [UCT]: 2024-08-17 17:56:37 Age [y:d:h:m:s]: 00:287:18:43:54
Block: 1090040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205587 RingCT/type: yes/0
Extra: 01775c2e8d3e26151ae1e49c55434653aabed7582edf87cb4e54288facf4d4cc6e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82709d736b66f0ba9bb5d09b43b775cf0f6b3d1b892cbeca202605d928ba6db4 0.600000000000 1564663 of 15

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": 1090050, "vin": [ { "gen": { "height": 1090040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82709d736b66f0ba9bb5d09b43b775cf0f6b3d1b892cbeca202605d928ba6db4" } } ], "extra": [ 1, 119, 92, 46, 141, 62, 38, 21, 26, 225, 228, 156, 85, 67, 70, 83, 170, 190, 215, 88, 46, 223, 135, 203, 78, 84, 40, 143, 172, 244, 212, 204, 110, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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