Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd479271e55f872a45ec092f77adf71f9388ffb823bb530d7521cd1d21aa5ad4

Tx prefix hash: 3132401a405073f8b8dd30f723ad460506e46b7cb4ab6c646909eb1f7a8ae9f3
Tx public key: 2cded622a4dc6e0daa1b3ec5c519714d86e5b2de90ec5c70b9777896869a1704
Timestamp: 1715154393 Timestamp [UCT]: 2024-05-08 07:46:33 Age [y:d:h:m:s]: 00:330:12:32:31
Block: 1017394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236239 RingCT/type: yes/0
Extra: 012cded622a4dc6e0daa1b3ec5c519714d86e5b2de90ec5c70b9777896869a17040211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 981e78e8e2f57324beaae5a24f0f4d323d301c8ee30398a6dd26ecba6f279ae0 0.600000000000 1481177 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": 1017404, "vin": [ { "gen": { "height": 1017394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "981e78e8e2f57324beaae5a24f0f4d323d301c8ee30398a6dd26ecba6f279ae0" } } ], "extra": [ 1, 44, 222, 214, 34, 164, 220, 110, 13, 170, 27, 62, 197, 197, 25, 113, 77, 134, 229, 178, 222, 144, 236, 92, 112, 185, 119, 120, 150, 134, 154, 23, 4, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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