Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14938617e8601fdc2306313249edb64c9be2a58c93c41d87e67caed1b1370cf6

Tx prefix hash: 541fe7e873342fe3ee21bcb0099edfa2197321409538230465e7726287925252
Tx public key: 423c08238e7a5f6b0a8c5ab939bb7aa28fbe1db499ce86c45e617f7791c161e8
Timestamp: 1702947300 Timestamp [UCT]: 2023-12-19 00:55:00 Age [y:d:h:m:s]: 01:154:15:39:58
Block: 916178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371705 RingCT/type: yes/0
Extra: 01423c08238e7a5f6b0a8c5ab939bb7aa28fbe1db499ce86c45e617f7791c161e802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43c56813cd2777e748f332632d412b1126dfc3c9df64e529d56b803f923fc813 0.600000000000 1373660 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": 916188, "vin": [ { "gen": { "height": 916178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43c56813cd2777e748f332632d412b1126dfc3c9df64e529d56b803f923fc813" } } ], "extra": [ 1, 66, 60, 8, 35, 142, 122, 95, 107, 10, 140, 90, 185, 57, 187, 122, 162, 143, 190, 29, 180, 153, 206, 134, 196, 94, 97, 127, 119, 145, 193, 97, 232, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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