Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0a3296c2792a36db8b3519c3fa3cac2d320f722149fd6dd2c147f71cc2df06f

Tx prefix hash: 4ab1c3eae11c529ad8e2150614102a3eadbdd33e33c5f952726369d897d01169
Tx public key: 14123a321d4a92f2076abcd67c534c08c1a87814861f3ed6f663aa96dd854019
Timestamp: 1703025764 Timestamp [UCT]: 2023-12-19 22:42:44 Age [y:d:h:m:s]: 01:149:15:03:35
Block: 916838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368087 RingCT/type: yes/0
Extra: 0114123a321d4a92f2076abcd67c534c08c1a87814861f3ed6f663aa96dd854019021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4adb6edc17707bcf0eb0bd47f96c0f04a854ccec57ef482cccb45ad18a67d676 0.600000000000 1374400 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": 916848, "vin": [ { "gen": { "height": 916838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4adb6edc17707bcf0eb0bd47f96c0f04a854ccec57ef482cccb45ad18a67d676" } } ], "extra": [ 1, 20, 18, 58, 50, 29, 74, 146, 242, 7, 106, 188, 214, 124, 83, 76, 8, 193, 168, 120, 20, 134, 31, 62, 214, 246, 99, 170, 150, 221, 133, 64, 25, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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