Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa5d461ffa9c2822f86f29f274947aee95748cbd0a98d5e135a6d48dd682be3

Tx prefix hash: 1610f2880d423885a477e09fe40b5e1979db3413d2321bf10366465598fd8b74
Tx public key: 00877a5fbd79f316e4fd8bc3862c4ca74387a5ffcc774e61d4e74c3602fbc051
Timestamp: 1582244454 Timestamp [UCT]: 2020-02-21 00:20:54 Age [y:d:h:m:s]: 04:313:11:10:55
Block: 69015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116676 RingCT/type: yes/0
Extra: 0100877a5fbd79f316e4fd8bc3862c4ca74387a5ffcc774e61d4e74c3602fbc05102110000000603d36d11000000000000000000

1 output(s) for total of 362.514565354000 dcy

stealth address amount amount idx
00: 994e07c4c0176c200819f990e3b9cb6e37f226ea722c8e6f4076bb28e22830ae 362.514565354000 127316 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": 69025, "vin": [ { "gen": { "height": 69015 } } ], "vout": [ { "amount": 362514565354, "target": { "key": "994e07c4c0176c200819f990e3b9cb6e37f226ea722c8e6f4076bb28e22830ae" } } ], "extra": [ 1, 0, 135, 122, 95, 189, 121, 243, 22, 228, 253, 139, 195, 134, 44, 76, 167, 67, 135, 165, 255, 204, 119, 78, 97, 212, 231, 76, 54, 2, 251, 192, 81, 2, 17, 0, 0, 0, 6, 3, 211, 109, 17, 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