Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b86facec5f53dd82553229e475d0d634f97d921a7270c2d3b5e03e96070c941c

Tx prefix hash: a0199d2c67f03c2e8d8c7a50fc63e18489fc775cd52deca39c9e6975e71a4982
Tx public key: fb0901789d84d3e37fdc99b8459bdb80c17c8b45be556b49dbd792530a2c0b86
Timestamp: 1631431265 Timestamp [UCT]: 2021-09-12 07:21:05 Age [y:d:h:m:s]: 03:077:08:28:05
Block: 332141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 830791 RingCT/type: yes/0
Extra: 01fb0901789d84d3e37fdc99b8459bdb80c17c8b45be556b49dbd792530a2c0b8602110000001bf60c5d7e000000000000000000

1 output(s) for total of 48.695556327000 dcy

stealth address amount amount idx
00: 34ae368720c5812a9b25a1405ec00006a18bbabd78eaca2676bbe15fc4ca901c 48.695556327000 686028 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": 332151, "vin": [ { "gen": { "height": 332141 } } ], "vout": [ { "amount": 48695556327, "target": { "key": "34ae368720c5812a9b25a1405ec00006a18bbabd78eaca2676bbe15fc4ca901c" } } ], "extra": [ 1, 251, 9, 1, 120, 157, 132, 211, 227, 127, 220, 153, 184, 69, 155, 219, 128, 193, 124, 139, 69, 190, 85, 107, 73, 219, 215, 146, 83, 10, 44, 11, 134, 2, 17, 0, 0, 0, 27, 246, 12, 93, 126, 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