Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9793b111ec0eea0e29a1172b60e7d1164f7908810e8a0571a6c116e554efacb7

Tx prefix hash: 2d7245a9741ee060ea6a91d90a7e9db969958397677ce5e9b87a09c2bd8e6002
Tx public key: fbb52c2a1d5ae894b7029ab33f01651233c850cbec9a8928cc4ca7891228f813
Timestamp: 1734902538 Timestamp [UCT]: 2024-12-22 21:22:18 Age [y:d:h:m:s]: 00:127:05:25:10
Block: 1181019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90709 RingCT/type: yes/0
Extra: 01fbb52c2a1d5ae894b7029ab33f01651233c850cbec9a8928cc4ca7891228f8130211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d629b2f34b52f0d431605b4cd8f0c58ec9d2b31f10e17b50ec2c14601f4cf1e2 0.600000000000 1667434 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": 1181029, "vin": [ { "gen": { "height": 1181019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d629b2f34b52f0d431605b4cd8f0c58ec9d2b31f10e17b50ec2c14601f4cf1e2" } } ], "extra": [ 1, 251, 181, 44, 42, 29, 90, 232, 148, 183, 2, 154, 179, 63, 1, 101, 18, 51, 200, 80, 203, 236, 154, 137, 40, 204, 76, 167, 137, 18, 40, 248, 19, 2, 17, 0, 0, 0, 7, 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