Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87612cf3aaeb539ba1e6d857f2197ca86f529530aba48319deb269ebbee395bd

Tx prefix hash: c9d1a7fc0d9b9ea5866b6dca3ef8e5394b41bdfd8eb5ba77131dadd55c8ccac7
Tx public key: 744b66288132146724d55e6fe77c5f93b6c9fe54a1e872b7112354b197fe78be
Timestamp: 1581243783 Timestamp [UCT]: 2020-02-09 10:23:03 Age [y:d:h:m:s]: 04:292:12:59:14
Block: 61217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101229 RingCT/type: yes/0
Extra: 01744b66288132146724d55e6fe77c5f93b6c9fe54a1e872b7112354b197fe78be02110000000b4ac5aa02000000000000000000

1 output(s) for total of 384.736582679000 dcy

stealth address amount amount idx
00: 1673ffda345ba0a9a415851f04c26099cd7236c37e649c9ff2033098b57b8f10 384.736582679000 112808 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": 61227, "vin": [ { "gen": { "height": 61217 } } ], "vout": [ { "amount": 384736582679, "target": { "key": "1673ffda345ba0a9a415851f04c26099cd7236c37e649c9ff2033098b57b8f10" } } ], "extra": [ 1, 116, 75, 102, 40, 129, 50, 20, 103, 36, 213, 94, 111, 231, 124, 95, 147, 182, 201, 254, 84, 161, 232, 114, 183, 17, 35, 84, 177, 151, 254, 120, 190, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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