Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c71c4d98992d047a06420621567b90cce8fc79d396e98d6da841ea0329e57c31

Tx prefix hash: 7a5f6019fcf78e851e2a858ce3f44de216890db50a7a1c62da2c60ebf89dffde
Tx public key: ea291ec35001cdb9ece816762ae5ee2253f5b98f3a81e2a0c98056c39c958e60
Timestamp: 1731866854 Timestamp [UCT]: 2024-11-17 18:07:34 Age [y:d:h:m:s]: 00:178:22:19:31
Block: 1155846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127723 RingCT/type: yes/0
Extra: 01ea291ec35001cdb9ece816762ae5ee2253f5b98f3a81e2a0c98056c39c958e600211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a893a83385be0ab22fce66994993880ea3a6a6b210064e915d2e5a23e0d00366 0.600000000000 1641465 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": 1155856, "vin": [ { "gen": { "height": 1155846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a893a83385be0ab22fce66994993880ea3a6a6b210064e915d2e5a23e0d00366" } } ], "extra": [ 1, 234, 41, 30, 195, 80, 1, 205, 185, 236, 232, 22, 118, 42, 229, 238, 34, 83, 245, 185, 143, 58, 129, 226, 160, 201, 128, 86, 195, 156, 149, 142, 96, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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