Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 846e3c095af0ad71165ef088e1f6cd04c5f20a2c1593dfc3264ee9f29eb2b186

Tx prefix hash: c019173d398168ea4d169f41af87bdf0809690dcccacba4098576b5bc85f4e01
Tx public key: 014d992e9d515c1ac9dedb96c581bc94a7de0363b7b3af1bc1a328551170215d
Timestamp: 1710124580 Timestamp [UCT]: 2024-03-11 02:36:20 Age [y:d:h:m:s]: 01:062:06:44:44
Block: 975697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305515 RingCT/type: yes/0
Extra: 01014d992e9d515c1ac9dedb96c581bc94a7de0363b7b3af1bc1a328551170215d02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a2b255f34f505674365c67cdcc4651bb059100ced1e5d4d05bc5bd85187a537 0.600000000000 1435670 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": 975707, "vin": [ { "gen": { "height": 975697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a2b255f34f505674365c67cdcc4651bb059100ced1e5d4d05bc5bd85187a537" } } ], "extra": [ 1, 1, 77, 153, 46, 157, 81, 92, 26, 201, 222, 219, 150, 197, 129, 188, 148, 167, 222, 3, 99, 183, 179, 175, 27, 193, 163, 40, 85, 17, 112, 33, 93, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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