Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82b73c688ee2ff7ce602c0dde7114ee300f56804989a745cfd40267016c7cc16

Tx prefix hash: 4c9ae1745b6f7d2244d5f6b3bafd1ce85d3bef25c2ca3cd525abd63edcd96ccc
Tx public key: 67894699ef062c3acad352a0451e131e3b0351ca60fc87509684f8162a29d3e7
Timestamp: 1710783576 Timestamp [UCT]: 2024-03-18 17:39:36 Age [y:d:h:m:s]: 01:038:19:07:49
Block: 981168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288712 RingCT/type: yes/0
Extra: 0167894699ef062c3acad352a0451e131e3b0351ca60fc87509684f8162a29d3e702110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7416aa43163df627a6d036a6aebaf0d964d1d0d1afb9fbea616865d0b79a39bd 0.600000000000 1441261 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": 981178, "vin": [ { "gen": { "height": 981168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7416aa43163df627a6d036a6aebaf0d964d1d0d1afb9fbea616865d0b79a39bd" } } ], "extra": [ 1, 103, 137, 70, 153, 239, 6, 44, 58, 202, 211, 82, 160, 69, 30, 19, 30, 59, 3, 81, 202, 96, 252, 135, 80, 150, 132, 248, 22, 42, 41, 211, 231, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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