Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07da3292383e0790b36fb0cab27be44adb4f31f2d3fdd6c9a23d8b1f5c77d022

Tx prefix hash: 00597ca42f2628729032b2c4b8f659a92a30259d32c4a31baeee76fdbeb5f553
Tx public key: 267b942df842c1c81b3c244cdb76c2be8ef8cbfc05a2f6ebb505a715b8a26b54
Timestamp: 1699288218 Timestamp [UCT]: 2023-11-06 16:30:18 Age [y:d:h:m:s]: 01:363:13:33:18
Block: 885840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518753 RingCT/type: yes/0
Extra: 01267b942df842c1c81b3c244cdb76c2be8ef8cbfc05a2f6ebb505a715b8a26b54021100000001faf35c9c000000000000000000

1 output(s) for total of 0.712597599000 dcy

stealth address amount amount idx
00: 89034bf50ade17c2aac43923e47d96580800edd32a98c4498aadcfd1fe78e0fc 0.712597599000 1341633 of 0

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": 885850, "vin": [ { "gen": { "height": 885840 } } ], "vout": [ { "amount": 712597599, "target": { "key": "89034bf50ade17c2aac43923e47d96580800edd32a98c4498aadcfd1fe78e0fc" } } ], "extra": [ 1, 38, 123, 148, 45, 248, 66, 193, 200, 27, 60, 36, 76, 219, 118, 194, 190, 142, 248, 203, 252, 5, 162, 246, 235, 181, 5, 167, 21, 184, 162, 107, 84, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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