Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a97dfd4d1b815719f6fae0a99993010bc9684e4fb9f4c010835319ecc52e6318

Tx prefix hash: b2d91a60be460aed215358e6a6986ef7b1f6f891db475e246e3dd71a99d8ccc3
Tx public key: 56044fe55df9c898bdeeb1c801e905997caeaf2d6a46eed975bc06c6bf90edf6
Timestamp: 1727644924 Timestamp [UCT]: 2024-09-29 21:22:04 Age [y:d:h:m:s]: 00:083:19:45:22
Block: 1120930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59961 RingCT/type: yes/0
Extra: 0156044fe55df9c898bdeeb1c801e905997caeaf2d6a46eed975bc06c6bf90edf602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131fec7a7dfc725343bd3484419daffd66c435f5b873c9d55e0a97553830dc73 0.600000000000 1603025 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": 1120940, "vin": [ { "gen": { "height": 1120930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131fec7a7dfc725343bd3484419daffd66c435f5b873c9d55e0a97553830dc73" } } ], "extra": [ 1, 86, 4, 79, 229, 93, 249, 200, 152, 189, 238, 177, 200, 1, 233, 5, 153, 124, 174, 175, 45, 106, 70, 238, 217, 117, 188, 6, 198, 191, 144, 237, 246, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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