Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f0b58c4b828454e131efea97785010d62d2fefeaf69a245fcdf8b88f5408a2

Tx prefix hash: 4810ef876a9dc2e5716fa81ce9a1f97644b3b72655914556a29f06cd531e4ed1
Tx public key: 2b223fe65893442a32f796955047694cf19cac1e5677eaaecd9cb4e5e2c86469
Timestamp: 1722274903 Timestamp [UCT]: 2024-07-29 17:41:43 Age [y:d:h:m:s]: 00:117:20:25:03
Block: 1076408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84330 RingCT/type: yes/0
Extra: 012b223fe65893442a32f796955047694cf19cac1e5677eaaecd9cb4e5e2c86469021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3da60ddff4f3c05fd2f6d7c6aae8da08fb13bf04893881661bf93423d12a52e 0.600000000000 1548945 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": 1076418, "vin": [ { "gen": { "height": 1076408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3da60ddff4f3c05fd2f6d7c6aae8da08fb13bf04893881661bf93423d12a52e" } } ], "extra": [ 1, 43, 34, 63, 230, 88, 147, 68, 42, 50, 247, 150, 149, 80, 71, 105, 76, 241, 156, 172, 30, 86, 119, 234, 174, 205, 156, 180, 229, 226, 200, 100, 105, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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