Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e2331819407bbc2c928272b2558472b056f137589a34af315e261a71d97405

Tx prefix hash: 986f5b1ec6e0b2abf159b26f3f295709b73cca4307ee799c50be7cae4eaf66b5
Tx public key: 6383f01b80b89bafffd4a89a3e440c7c51bc374a5bbb8c3c798040c7da6649bb
Timestamp: 1711377810 Timestamp [UCT]: 2024-03-25 14:43:30 Age [y:d:h:m:s]: 01:228:22:01:22
Block: 986097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422276 RingCT/type: yes/0
Extra: 016383f01b80b89bafffd4a89a3e440c7c51bc374a5bbb8c3c798040c7da6649bb02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1bfcde04f8ef60ce8ad1a0cb77058dad8310d38d234a55855caffcba5fc92a1 0.600000000000 1446322 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": 986107, "vin": [ { "gen": { "height": 986097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1bfcde04f8ef60ce8ad1a0cb77058dad8310d38d234a55855caffcba5fc92a1" } } ], "extra": [ 1, 99, 131, 240, 27, 128, 184, 155, 175, 255, 212, 168, 154, 62, 68, 12, 124, 81, 188, 55, 74, 91, 187, 140, 60, 121, 128, 64, 199, 218, 102, 73, 187, 2, 17, 0, 0, 0, 9, 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