Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79902e66c5dcfee88b8a1c28ac26dfa8bbd58e419ff1373d9b114abb65cdc287

Tx prefix hash: fed32c42897261ef244980a2dbbc72783d720004df24095d02d4b8ce4a56e4f5
Tx public key: 3f54055f31d5fd542df2b49bff46c16ba53792758b4ebe61a177f28484939d3c
Timestamp: 1726430160 Timestamp [UCT]: 2024-09-15 19:56:00 Age [y:d:h:m:s]: 00:182:15:35:32
Block: 1110862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130386 RingCT/type: yes/0
Extra: 013f54055f31d5fd542df2b49bff46c16ba53792758b4ebe61a177f28484939d3c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79645aa083a178bf316b77b5ad3b6b96d7b0eb184dfaad4dad3b7b027afd4cf1 0.600000000000 1589623 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": 1110872, "vin": [ { "gen": { "height": 1110862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79645aa083a178bf316b77b5ad3b6b96d7b0eb184dfaad4dad3b7b027afd4cf1" } } ], "extra": [ 1, 63, 84, 5, 95, 49, 213, 253, 84, 45, 242, 180, 155, 255, 70, 193, 107, 165, 55, 146, 117, 139, 78, 190, 97, 161, 119, 242, 132, 132, 147, 157, 60, 2, 17, 0, 0, 0, 3, 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