Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41304f54ec52a4d5ad7292982f47b28c97b8bf37f0f736b71b4e5284ab173c55

Tx prefix hash: 7613c091479365a89fc453a4cf50bbaa43ff169caccb08c717dfbb5cdbdff26e
Tx public key: f16ebfe8b787953ac0272a80a76f32833d2c18b1b56ad812d9a99080a17f05fa
Timestamp: 1682820308 Timestamp [UCT]: 2023-04-30 02:05:08 Age [y:d:h:m:s]: 01:346:14:12:17
Block: 749567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508960 RingCT/type: yes/0
Extra: 01f16ebfe8b787953ac0272a80a76f32833d2c18b1b56ad812d9a99080a17f05fa021100000003faf35c9c000000000000000000

1 output(s) for total of 2.015457166000 dcy

stealth address amount amount idx
00: 46e71701e1387fd4aa2cc0d2ab3c6d9c8e6300210150a7c6dc1fe19f215fe225 2.015457166000 1197550 of 0

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": 749577, "vin": [ { "gen": { "height": 749567 } } ], "vout": [ { "amount": 2015457166, "target": { "key": "46e71701e1387fd4aa2cc0d2ab3c6d9c8e6300210150a7c6dc1fe19f215fe225" } } ], "extra": [ 1, 241, 110, 191, 232, 183, 135, 149, 58, 192, 39, 42, 128, 167, 111, 50, 131, 61, 44, 24, 177, 181, 106, 216, 18, 217, 169, 144, 128, 161, 127, 5, 250, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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