Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62dffd1f7a6b907dda27866227c28267ea4496088aa1bfc9edb7de75d49b14c5

Tx prefix hash: 9996b8d554c4efaa14965f234b336b7058cd46202f7a1cedfd619d66963705bd
Tx public key: 4863e4e74f13645425af79df7dc3e6d1e6e97e85264e89938a341a029694b7d7
Timestamp: 1703719184 Timestamp [UCT]: 2023-12-27 23:19:44 Age [y:d:h:m:s]: 01:116:09:48:39
Block: 922584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344313 RingCT/type: yes/0
Extra: 014863e4e74f13645425af79df7dc3e6d1e6e97e85264e89938a341a029694b7d70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4625acbeb4d024ab50813e884a7be27eb15a38ffecbda79fe83f45e7132d46da 0.600000000000 1380288 of 15

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": 922594, "vin": [ { "gen": { "height": 922584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4625acbeb4d024ab50813e884a7be27eb15a38ffecbda79fe83f45e7132d46da" } } ], "extra": [ 1, 72, 99, 228, 231, 79, 19, 100, 84, 37, 175, 121, 223, 125, 195, 230, 209, 230, 233, 126, 133, 38, 78, 137, 147, 138, 52, 26, 2, 150, 148, 183, 215, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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