Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7daaa255fd54633e09fd792990b48da3e232d0ecfe329b5b2f3103267ef3eb

Tx prefix hash: ff930199d8b6c22572c5e0bf83f6a08a3402f06bf9da2d810abb644ade5ef111
Tx public key: 80be429d7c8bfd80b1c8cb2c972a2924d9a6bed8c5f75b004fd2c61245cb01db
Timestamp: 1657286796 Timestamp [UCT]: 2022-07-08 13:26:36 Age [y:d:h:m:s]: 02:179:03:56:47
Block: 539349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649384 RingCT/type: yes/0
Extra: 0180be429d7c8bfd80b1c8cb2c972a2924d9a6bed8c5f75b004fd2c61245cb01db021100000015bf7ee4e7000000000000000000

1 output(s) for total of 10.021045095000 dcy

stealth address amount amount idx
00: 3a31ad4cea64bca6372a6618a41ba8a99c960e99fc32e3fcc792183435b5eba1 10.021045095000 969440 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": 539359, "vin": [ { "gen": { "height": 539349 } } ], "vout": [ { "amount": 10021045095, "target": { "key": "3a31ad4cea64bca6372a6618a41ba8a99c960e99fc32e3fcc792183435b5eba1" } } ], "extra": [ 1, 128, 190, 66, 157, 124, 139, 253, 128, 177, 200, 203, 44, 151, 42, 41, 36, 217, 166, 190, 216, 197, 247, 91, 0, 79, 210, 198, 18, 69, 203, 1, 219, 2, 17, 0, 0, 0, 21, 191, 126, 228, 231, 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