Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63cebca12946ca2be302811bfeb54a5f06a22f9f574f871789d9c76b65702f83

Tx prefix hash: 944779a11455df0bf73b592ffe2344ecca020ce81e4edd9a8215ce6a4fe09843
Tx public key: 1ef8a746ea8a75708a3428c078a7bc847b1d8089519d76d8cc8c6a0880e693d5
Timestamp: 1730018230 Timestamp [UCT]: 2024-10-27 08:37:10 Age [y:d:h:m:s]: 00:145:22:20:48
Block: 1140577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104085 RingCT/type: yes/0
Extra: 011ef8a746ea8a75708a3428c078a7bc847b1d8089519d76d8cc8c6a0880e693d5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54337ad514fbcf62b02bfca8ac3b88c6a77d1540d8406445e95f739ba9d8263d 0.600000000000 1624378 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": 1140587, "vin": [ { "gen": { "height": 1140577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54337ad514fbcf62b02bfca8ac3b88c6a77d1540d8406445e95f739ba9d8263d" } } ], "extra": [ 1, 30, 248, 167, 70, 234, 138, 117, 112, 138, 52, 40, 192, 120, 167, 188, 132, 123, 29, 128, 137, 81, 157, 118, 216, 204, 140, 106, 8, 128, 230, 147, 213, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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