Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f9dbeef23dc9a34d57defead12fc01f5097ad0b1e52ea96c8f70cab71690647

Tx prefix hash: a33e00207eaa557732d286ed2dc45de6a175bd87bb43946bbd5598ec0ea610aa
Tx public key: b640134c5e7b03ea589c948e3fe9273332fdf09feeec41d4b794c9fee0747f7b
Timestamp: 1725556099 Timestamp [UCT]: 2024-09-05 17:08:19 Age [y:d:h:m:s]: 00:203:20:32:10
Block: 1103624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145529 RingCT/type: yes/0
Extra: 01b640134c5e7b03ea589c948e3fe9273332fdf09feeec41d4b794c9fee0747f7b02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4558090c9b998e8210e26dd1bd544f78192e99cd4e0dbde17d693f07d21c182c 0.600000000000 1580525 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": 1103634, "vin": [ { "gen": { "height": 1103624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4558090c9b998e8210e26dd1bd544f78192e99cd4e0dbde17d693f07d21c182c" } } ], "extra": [ 1, 182, 64, 19, 76, 94, 123, 3, 234, 88, 156, 148, 142, 63, 233, 39, 51, 50, 253, 240, 159, 238, 236, 65, 212, 183, 148, 201, 254, 224, 116, 127, 123, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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