Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23262cf08003f0195b159f2a4674d3efd815849fc4cd39d926f08d40193e68a3

Tx prefix hash: 7e978da43059d3ddc6008eae940385823634194f38f12e43b027a138f1c68c50
Tx public key: fcc3649e866f120f0638484d42168f4f16e618fbd612b6dc2b86c603ef66326a
Timestamp: 1697125104 Timestamp [UCT]: 2023-10-12 15:38:24 Age [y:d:h:m:s]: 01:177:22:18:22
Block: 868131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388168 RingCT/type: yes/0
Extra: 01fcc3649e866f120f0638484d42168f4f16e618fbd612b6dc2b86c603ef66326a0211000000134b8f5122000000000000000000

1 output(s) for total of 0.815683446000 dcy

stealth address amount amount idx
00: 7a61bb9165b15cf4f07229edea496063608b742123f82f91405791e95418af9e 0.815683446000 1322902 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": 868141, "vin": [ { "gen": { "height": 868131 } } ], "vout": [ { "amount": 815683446, "target": { "key": "7a61bb9165b15cf4f07229edea496063608b742123f82f91405791e95418af9e" } } ], "extra": [ 1, 252, 195, 100, 158, 134, 111, 18, 15, 6, 56, 72, 77, 66, 22, 143, 79, 22, 230, 24, 251, 214, 18, 182, 220, 43, 134, 198, 3, 239, 102, 50, 106, 2, 17, 0, 0, 0, 19, 75, 143, 81, 34, 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