Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9faac83dcab96a528d46c4f08af9368270b84869db0c1fee5122fe3df73efdf

Tx prefix hash: fb116e5bf8c38d983d63a9b64d58327e67979b20f29763f14edda340a090318d
Tx public key: fe612c64638cdfa08c68bc8d42df569f89d527208bc0fea500ef1f4da4065f91
Timestamp: 1700495035 Timestamp [UCT]: 2023-11-20 15:43:55 Age [y:d:h:m:s]: 01:178:07:39:11
Block: 895844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388640 RingCT/type: yes/0
Extra: 01fe612c64638cdfa08c68bc8d42df569f89d527208bc0fea500ef1f4da4065f9102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.660232555000 dcy

stealth address amount amount idx
00: 6263d6e330f3fd9caead816ee76a630847c55a9f210ed6ab42f7f3d75fd31e2b 0.660232555000 1352091 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": 895854, "vin": [ { "gen": { "height": 895844 } } ], "vout": [ { "amount": 660232555, "target": { "key": "6263d6e330f3fd9caead816ee76a630847c55a9f210ed6ab42f7f3d75fd31e2b" } } ], "extra": [ 1, 254, 97, 44, 100, 99, 140, 223, 160, 140, 104, 188, 141, 66, 223, 86, 159, 137, 213, 39, 32, 139, 192, 254, 165, 0, 239, 31, 77, 164, 6, 95, 145, 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