Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441ba37d4d729d515f2b3cbc3c2826f4d0612fd8b37363d352dc629e368b3f1a

Tx prefix hash: 35a61b5dfed23947715a46e5586822a43ff18da6141139383b59b806e3cbaa91
Tx public key: fe14d4f40bfd38ca8c6e62d68490b4ea69d62f066635bdc89126b325ce3a2326
Timestamp: 1736999471 Timestamp [UCT]: 2025-01-16 03:51:11 Age [y:d:h:m:s]: 00:153:20:33:43
Block: 1198336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109671 RingCT/type: yes/0
Extra: 01fe14d4f40bfd38ca8c6e62d68490b4ea69d62f066635bdc89126b325ce3a232602110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2332a27cba35e8bccf7aeb10b64d5faa8323dfa6b298c3d9d6e1954f5bb09397 0.600000000000 1684959 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": 1198346, "vin": [ { "gen": { "height": 1198336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2332a27cba35e8bccf7aeb10b64d5faa8323dfa6b298c3d9d6e1954f5bb09397" } } ], "extra": [ 1, 254, 20, 212, 244, 11, 253, 56, 202, 140, 110, 98, 214, 132, 144, 180, 234, 105, 214, 47, 6, 102, 53, 189, 200, 145, 38, 179, 37, 206, 58, 35, 38, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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