Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48a4bc9ea1836806eee50f672a7764f4fafc7f2f24564dd33e4584b13ac8b1f

Tx prefix hash: 9656dfdc7eb6ca120245afe712fbeb3a9ca38c5cb560a304da599951148c3df0
Tx public key: 9b4ca116d23c1e9000a78d66ba885ee24e693583fd54c870e54372e4dc0bff36
Timestamp: 1731277661 Timestamp [UCT]: 2024-11-10 22:27:41 Age [y:d:h:m:s]: 00:360:07:14:25
Block: 1150969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255032 RingCT/type: yes/0
Extra: 019b4ca116d23c1e9000a78d66ba885ee24e693583fd54c870e54372e4dc0bff360211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64dbebc276b4d94c80c26cb5d12c653b3ea5a87381915f2d37aa68ebf68408bf 0.600000000000 1636414 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": 1150979, "vin": [ { "gen": { "height": 1150969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64dbebc276b4d94c80c26cb5d12c653b3ea5a87381915f2d37aa68ebf68408bf" } } ], "extra": [ 1, 155, 76, 161, 22, 210, 60, 30, 144, 0, 167, 141, 102, 186, 136, 94, 226, 78, 105, 53, 131, 253, 84, 200, 112, 229, 67, 114, 228, 220, 11, 255, 54, 2, 17, 0, 0, 0, 4, 31, 10, 83, 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