Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a243af5364063175530256509b3191a71b202c38028e67cc044f004ae3aa01

Tx prefix hash: 6af26f1d0843a74c8e355ce3e98d2aac703e53a359ca7ccd6bf1ab0b9d6e6482
Tx public key: 2a832ba8507e68f81ab0e3a57b9fc7869f7223c96024dfa45419986fdb02f2de
Timestamp: 1708724627 Timestamp [UCT]: 2024-02-23 21:43:47 Age [y:d:h:m:s]: 01:344:12:00:59
Block: 964075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504884 RingCT/type: yes/0
Extra: 012a832ba8507e68f81ab0e3a57b9fc7869f7223c96024dfa45419986fdb02f2de021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f61fc7f2b414efea3f4e4f8d6376ad08f8148cc6deec6d42d6f956337fdaf16 0.600000000000 1423802 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": 964085, "vin": [ { "gen": { "height": 964075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f61fc7f2b414efea3f4e4f8d6376ad08f8148cc6deec6d42d6f956337fdaf16" } } ], "extra": [ 1, 42, 131, 43, 168, 80, 126, 104, 248, 26, 176, 227, 165, 123, 159, 199, 134, 159, 114, 35, 201, 96, 36, 223, 164, 84, 25, 152, 111, 219, 2, 242, 222, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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