Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 602b0ca07eb922196fd5bb96c40d7d3c8408bfc28522d85913083f3811686ab5

Tx prefix hash: 8ebde168441a8f1c53ebfc0dae463b9aa2846ae22e997d00d5d6a690691a5d06
Tx public key: 824a0f449657eb2b81fa45357a221f3fc4c4f8e4f54750d41b6da6cda1c32945
Timestamp: 1734613473 Timestamp [UCT]: 2024-12-19 13:04:33 Age [y:d:h:m:s]: 00:105:10:08:28
Block: 1178624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75100 RingCT/type: yes/0
Extra: 01824a0f449657eb2b81fa45357a221f3fc4c4f8e4f54750d41b6da6cda1c32945021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b85a397a3e2e6d55f8839d99b2dd0b20ee647409131512bf19d4765b8de9e99d 0.600000000000 1665013 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": 1178634, "vin": [ { "gen": { "height": 1178624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b85a397a3e2e6d55f8839d99b2dd0b20ee647409131512bf19d4765b8de9e99d" } } ], "extra": [ 1, 130, 74, 15, 68, 150, 87, 235, 43, 129, 250, 69, 53, 122, 34, 31, 63, 196, 196, 248, 228, 245, 71, 80, 212, 27, 109, 166, 205, 161, 195, 41, 69, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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