Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e698fcec3436c5b3d1eb149ae87f50d1407d87d7d1f2f70861e10f72568a276

Tx prefix hash: 901e9b18ccc1b6a529299cd3c25840a5613e40e3dc287d383ba74640a8045eae
Tx public key: fe76b995780f819c982441fcbc2a416264ac5fb2e95e4cd5276e04cde3de0a8e
Timestamp: 1731572928 Timestamp [UCT]: 2024-11-14 08:28:48 Age [y:d:h:m:s]: 00:143:16:28:03
Block: 1153407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102509 RingCT/type: yes/0
Extra: 01fe76b995780f819c982441fcbc2a416264ac5fb2e95e4cd5276e04cde3de0a8e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3c700f52c291735c9a9567076455620ab212301018b7fbe37c14e369186c80f 0.600000000000 1639016 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": 1153417, "vin": [ { "gen": { "height": 1153407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3c700f52c291735c9a9567076455620ab212301018b7fbe37c14e369186c80f" } } ], "extra": [ 1, 254, 118, 185, 149, 120, 15, 129, 156, 152, 36, 65, 252, 188, 42, 65, 98, 100, 172, 95, 178, 233, 94, 76, 213, 39, 110, 4, 205, 227, 222, 10, 142, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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