Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091ae49028b5c876c39bee56b1608f56b1c8bd645541395205a6f380ff8f1303

Tx prefix hash: ec969247f5893654ec034e3084b3cbc678b0f362ec28d03310f42ea09447e2c9
Tx public key: b17403e5396438276c5eb9eaf713b2b8c9d4987dabbb4fe48b504a7e45aaf50d
Timestamp: 1702485753 Timestamp [UCT]: 2023-12-13 16:42:33 Age [y:d:h:m:s]: 01:126:21:52:49
Block: 912371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351834 RingCT/type: yes/0
Extra: 01b17403e5396438276c5eb9eaf713b2b8c9d4987dabbb4fe48b504a7e45aaf50d02110000001dfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f3d4e049279b12bee78289ecef228f24859abbad6ac4901f92e6b6d71ae3397 0.600000000000 1369597 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": 912381, "vin": [ { "gen": { "height": 912371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f3d4e049279b12bee78289ecef228f24859abbad6ac4901f92e6b6d71ae3397" } } ], "extra": [ 1, 177, 116, 3, 229, 57, 100, 56, 39, 108, 94, 185, 234, 247, 19, 178, 184, 201, 212, 152, 125, 171, 187, 79, 228, 139, 80, 74, 126, 69, 170, 245, 13, 2, 17, 0, 0, 0, 29, 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