Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ab6f6532355b58e6391a09a801baf22db849917d9dc7cc0b370cbbbb16a6ef

Tx prefix hash: 9a774e607fa58bb2d2f14a41699e9712a63dc93ced5bc9bd0b0223a614fd28eb
Tx public key: 0158ab280b093e2a0d94ee7c623565110226c9c2fb23b20a22cc4b1635e42ffe
Timestamp: 1577489172 Timestamp [UCT]: 2019-12-27 23:26:12 Age [y:d:h:m:s]: 05:135:20:07:09
Block: 33129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246951 RingCT/type: yes/0
Extra: 010158ab280b093e2a0d94ee7c623565110226c9c2fb23b20a22cc4b1635e42ffe02110000000b4ac5aa02000000000000000000

1 output(s) for total of 476.684168168000 dcy

stealth address amount amount idx
00: 0139f4ac787991b176d929045c6cde7069455dc2ba972982dc477baef487f054 476.684168168000 55336 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": 33139, "vin": [ { "gen": { "height": 33129 } } ], "vout": [ { "amount": 476684168168, "target": { "key": "0139f4ac787991b176d929045c6cde7069455dc2ba972982dc477baef487f054" } } ], "extra": [ 1, 1, 88, 171, 40, 11, 9, 62, 42, 13, 148, 238, 124, 98, 53, 101, 17, 2, 38, 201, 194, 251, 35, 178, 10, 34, 204, 75, 22, 53, 228, 47, 254, 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