Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac0c8ffc0dcf8ac8ab1cf564235f0f29642edb70bf763f8d95e1686eca9f0f2

Tx prefix hash: 0570887ce8ca3193f9d27e646158ec8cca2929599058780002a0dc4c46c4c135
Tx public key: 7c9a7e7015d758cd6b17dd1e110cc88a6c66672e0a44d49b029d3abedefd4448
Timestamp: 1730794368 Timestamp [UCT]: 2024-11-05 08:12:48 Age [y:d:h:m:s]: 00:171:19:37:56
Block: 1146965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122634 RingCT/type: yes/0
Extra: 017c9a7e7015d758cd6b17dd1e110cc88a6c66672e0a44d49b029d3abedefd4448021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 480d83058c9a8e930b432972a2ab4fcd1365702a741ce66444b7a075f81cb744 0.600000000000 1631658 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": 1146975, "vin": [ { "gen": { "height": 1146965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "480d83058c9a8e930b432972a2ab4fcd1365702a741ce66444b7a075f81cb744" } } ], "extra": [ 1, 124, 154, 126, 112, 21, 215, 88, 205, 107, 23, 221, 30, 17, 12, 200, 138, 108, 102, 103, 46, 10, 68, 212, 155, 2, 157, 58, 190, 222, 253, 68, 72, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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