Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b814c46183a13aa0c344efbff7dc424737400b187569cf30bcd683a7536f0e34

Tx prefix hash: 8963bd3de1c80cb21b805f26b47238f2b86f2ad7979362d03c963c52a7a7fb51
Tx public key: ad011bf9ce0f0b94b5acf4023bbc49328ad2deb14efb753f34d3e5b74908161c
Timestamp: 1714292625 Timestamp [UCT]: 2024-04-28 08:23:45 Age [y:d:h:m:s]: 00:305:11:03:04
Block: 1010231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218341 RingCT/type: yes/0
Extra: 01ad011bf9ce0f0b94b5acf4023bbc49328ad2deb14efb753f34d3e5b74908161c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5600748e4f318729e830a8f0119dbccf3af973fa9f7f349e2bd53fda06f1e3fb 0.600000000000 1472129 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": 1010241, "vin": [ { "gen": { "height": 1010231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5600748e4f318729e830a8f0119dbccf3af973fa9f7f349e2bd53fda06f1e3fb" } } ], "extra": [ 1, 173, 1, 27, 249, 206, 15, 11, 148, 181, 172, 244, 2, 59, 188, 73, 50, 138, 210, 222, 177, 78, 251, 117, 63, 52, 211, 229, 183, 73, 8, 22, 28, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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