Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e8f109b12b67f8501b8ad2f4f6f053a49d528923951514e4236d9ad0d70c669

Tx prefix hash: 9e7ac97365008556da027678e3bcdf1e5092cb821e3e175608bcbab5c885527f
Tx public key: f69eb80c53b4f6ae002293f8413f6e4331db2e1525489d65b2315e749f7340da
Timestamp: 1710561987 Timestamp [UCT]: 2024-03-16 04:06:27 Age [y:d:h:m:s]: 01:015:14:25:15
Block: 979320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272123 RingCT/type: yes/0
Extra: 01f69eb80c53b4f6ae002293f8413f6e4331db2e1525489d65b2315e749f7340da0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c0c5b94d31543190bc1acbd8b2a2d8f7346a1efcbe5c53058d058046d0d9775 0.600000000000 1439353 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": 979330, "vin": [ { "gen": { "height": 979320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c0c5b94d31543190bc1acbd8b2a2d8f7346a1efcbe5c53058d058046d0d9775" } } ], "extra": [ 1, 246, 158, 184, 12, 83, 180, 246, 174, 0, 34, 147, 248, 65, 63, 110, 67, 49, 219, 46, 21, 37, 72, 157, 101, 178, 49, 94, 116, 159, 115, 64, 218, 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