Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3af8fe22678ed593c907d330d66dc9a982962bc220c2f1b27eb38adcb30dfe3d

Tx prefix hash: aea7aa0253a433f8c67a40b2a8c257f2631e1021ca66145c7896cc0d4364a744
Tx public key: c70104e8cb92f9817f39517da9b3e177fe11ca82e9c8bf34a18c61839307dc3a
Timestamp: 1714464715 Timestamp [UCT]: 2024-04-30 08:11:55 Age [y:d:h:m:s]: 00:342:20:33:28
Block: 1011659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245077 RingCT/type: yes/0
Extra: 01c70104e8cb92f9817f39517da9b3e177fe11ca82e9c8bf34a18c61839307dc3a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b7eebc86677df2cbe57646b0a29262617519dfed1f8b7bdf846cd3ef03ec96b 0.600000000000 1473945 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": 1011669, "vin": [ { "gen": { "height": 1011659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b7eebc86677df2cbe57646b0a29262617519dfed1f8b7bdf846cd3ef03ec96b" } } ], "extra": [ 1, 199, 1, 4, 232, 203, 146, 249, 129, 127, 57, 81, 125, 169, 179, 225, 119, 254, 17, 202, 130, 233, 200, 191, 52, 161, 140, 97, 131, 147, 7, 220, 58, 2, 17, 0, 0, 0, 1, 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