Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9909e48f5b7361e41bf8f24a4601fca464c8af9a4c6589003f1052b771aaf95f

Tx prefix hash: f11028297d0b6d5b8c52a0daa5d389880c829d7184a8647efcdd3b8a7aedab6b
Tx public key: 6ff602ca45317337260d9f58653d03ebfb5bd1a63ec46b19eb7c61fffff1f8db
Timestamp: 1672725054 Timestamp [UCT]: 2023-01-03 05:50:54 Age [y:d:h:m:s]: 01:334:08:46:23
Block: 666483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499994 RingCT/type: yes/0
Extra: 016ff602ca45317337260d9f58653d03ebfb5bd1a63ec46b19eb7c61fffff1f8db02110000000152542ceb000000000000000000

1 output(s) for total of 3.798963432000 dcy

stealth address amount amount idx
00: 2b05be88bb10ec58c862810b373733d8a7bd4f135712a9fe409234ec694b12e5 3.798963432000 1107594 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": 666493, "vin": [ { "gen": { "height": 666483 } } ], "vout": [ { "amount": 3798963432, "target": { "key": "2b05be88bb10ec58c862810b373733d8a7bd4f135712a9fe409234ec694b12e5" } } ], "extra": [ 1, 111, 246, 2, 202, 69, 49, 115, 55, 38, 13, 159, 88, 101, 61, 3, 235, 251, 91, 209, 166, 62, 196, 107, 25, 235, 124, 97, 255, 255, 241, 248, 219, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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