Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29f4f4b32abf9f34f934a9ca0cf3ef338dcd6b69bd7d74e505fc46096be127ce

Tx prefix hash: dbc251321c3b55832be019cc0318946e5ab3fbbf97b67e3d90bf6c885830a966
Tx public key: 29f578361f12058ae17f855be06343b92f9a5d6becd4853e51a12dab3027cb69
Timestamp: 1608172917 Timestamp [UCT]: 2020-12-17 02:41:57 Age [y:d:h:m:s]: 04:145:19:04:37
Block: 163551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116597 RingCT/type: yes/0
Extra: 0129f578361f12058ae17f855be06343b92f9a5d6becd4853e51a12dab3027cb6902110000009427e2517e000000000000000000

1 output(s) for total of 176.242570179000 dcy

stealth address amount amount idx
00: 996cc70dfe92f8f021fb7a8e10055dfd378236195b0ee1454deb564e2a3b62e3 176.242570179000 293688 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": 163561, "vin": [ { "gen": { "height": 163551 } } ], "vout": [ { "amount": 176242570179, "target": { "key": "996cc70dfe92f8f021fb7a8e10055dfd378236195b0ee1454deb564e2a3b62e3" } } ], "extra": [ 1, 41, 245, 120, 54, 31, 18, 5, 138, 225, 127, 133, 91, 224, 99, 67, 185, 47, 154, 93, 107, 236, 212, 133, 62, 81, 161, 45, 171, 48, 39, 203, 105, 2, 17, 0, 0, 0, 148, 39, 226, 81, 126, 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