Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf89e2dd41569deb6f74ccb1722d9d085f2e6c6d12e0821c6929ebe4b60825b4

Tx prefix hash: a8d4d69c9449c4e4ac10a5aa05882174c7b2451c5b7ac1f55dd4a18a726d33a9
Tx public key: fd4735243c42053578ed7c010dd4859f44ed701f694d534f8cddd57c4a69da3f
Timestamp: 1643346557 Timestamp [UCT]: 2022-01-28 05:09:17 Age [y:d:h:m:s]: 02:344:09:35:21
Block: 426842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764688 RingCT/type: yes/0
Extra: 01fd4735243c42053578ed7c010dd4859f44ed701f694d534f8cddd57c4a69da3f02110000000dbf7ee4e7000000000000000000

1 output(s) for total of 23.642618592000 dcy

stealth address amount amount idx
00: ae37b1f8e2487853a06d6b0a783c05aae58d9d9e154d99a847b44c75127d8a1c 23.642618592000 835806 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": 426852, "vin": [ { "gen": { "height": 426842 } } ], "vout": [ { "amount": 23642618592, "target": { "key": "ae37b1f8e2487853a06d6b0a783c05aae58d9d9e154d99a847b44c75127d8a1c" } } ], "extra": [ 1, 253, 71, 53, 36, 60, 66, 5, 53, 120, 237, 124, 1, 13, 212, 133, 159, 68, 237, 112, 31, 105, 77, 83, 79, 140, 221, 213, 124, 74, 105, 218, 63, 2, 17, 0, 0, 0, 13, 191, 126, 228, 231, 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