Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5139fe02d32faf3da792054c82df6da2d7e4f050cf9e857e4d873e77340dd689

Tx prefix hash: fcd92ff29db5ee1bd474e89681a33896acd8700e29f2f8dd56a6becfb4ce2880
Tx public key: 3a2fbaa2e7243110b8b2b70f28056c8a06441e028f660bcd6f34c4544e92042f
Timestamp: 1703675225 Timestamp [UCT]: 2023-12-27 11:07:05 Age [y:d:h:m:s]: 01:080:15:41:36
Block: 922212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318762 RingCT/type: yes/0
Extra: 013a2fbaa2e7243110b8b2b70f28056c8a06441e028f660bcd6f34c4544e92042f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9f8bdaa299e77512399872fe1252a8f8961d032163e108ee04d31402e1321b 0.600000000000 1379908 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": 922222, "vin": [ { "gen": { "height": 922212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9f8bdaa299e77512399872fe1252a8f8961d032163e108ee04d31402e1321b" } } ], "extra": [ 1, 58, 47, 186, 162, 231, 36, 49, 16, 184, 178, 183, 15, 40, 5, 108, 138, 6, 68, 30, 2, 143, 102, 11, 205, 111, 52, 196, 84, 78, 146, 4, 47, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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