Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58df9c164acf8e43b0d7bc571f1c96a06db644a8b62d6dd56297e0d0c5dcd251

Tx prefix hash: 53e2b8a8f295a399945eeb78f6af4d8c021610ffbd9055095b78b4675e8afa01
Tx public key: 1581d92561c4a05e88f0de0d10469626fd1738d70ffaa5f1098e744f6012df86
Timestamp: 1721914992 Timestamp [UCT]: 2024-07-25 13:43:12 Age [y:d:h:m:s]: 00:185:16:17:11
Block: 1073429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132609 RingCT/type: yes/0
Extra: 011581d92561c4a05e88f0de0d10469626fd1738d70ffaa5f1098e744f6012df86021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d72ef41fc0fa0003eab0456fc4e3e0d614b1751622c5c9048c6f71cd46e4547e 0.600000000000 1545932 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": 1073439, "vin": [ { "gen": { "height": 1073429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d72ef41fc0fa0003eab0456fc4e3e0d614b1751622c5c9048c6f71cd46e4547e" } } ], "extra": [ 1, 21, 129, 217, 37, 97, 196, 160, 94, 136, 240, 222, 13, 16, 70, 150, 38, 253, 23, 56, 215, 15, 250, 165, 241, 9, 142, 116, 79, 96, 18, 223, 134, 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