Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635eeb4a6d421a3b61beed2de7389e89a91d99aafc1d094e19d458bfbc8fe33c

Tx prefix hash: 3f25c34c7c9a821c62ea251c78cbd2f29f920c3e771f594f0b5e04d02baf986a
Tx public key: ed5ab03cb51db9dfdd999c57b5f01f092539ca2dd0fcd8250e531a38447abf17
Timestamp: 1574484877 Timestamp [UCT]: 2019-11-23 04:54:37 Age [y:d:h:m:s]: 05:078:10:57:59
Block: 15065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1199117 RingCT/type: yes/0
Extra: 01ed5ab03cb51db9dfdd999c57b5f01f092539ca2dd0fcd8250e531a38447abf1702110000002efc8b7a00000000000000000000

1 output(s) for total of 547.122134790000 dcy

stealth address amount amount idx
00: 822dd78a7b390a96b3bb2a939edb313527674ac48a74f40cc4080a7eef3e7cea 547.122134790000 19853 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": 15075, "vin": [ { "gen": { "height": 15065 } } ], "vout": [ { "amount": 547122134790, "target": { "key": "822dd78a7b390a96b3bb2a939edb313527674ac48a74f40cc4080a7eef3e7cea" } } ], "extra": [ 1, 237, 90, 176, 60, 181, 29, 185, 223, 221, 153, 156, 87, 181, 240, 31, 9, 37, 57, 202, 45, 208, 252, 216, 37, 14, 83, 26, 56, 68, 122, 191, 23, 2, 17, 0, 0, 0, 46, 252, 139, 122, 0, 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