Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f585237af6de9d06f3d36ce324a623de9a7cd887e864282b6ccf448ce8905c7a

Tx prefix hash: d1977564eef4b3cde07020ceb24389899aa532190d53fc7d717d8ba684f39d5e
Tx public key: 0c5115eb0e6ae306c49c8c466041d2c752bd7aaf209479c66fc75b5efae4541b
Timestamp: 1732345530 Timestamp [UCT]: 2024-11-23 07:05:30 Age [y:d:h:m:s]: 00:000:14:39:38
Block: 1159813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427 RingCT/type: yes/0
Extra: 010c5115eb0e6ae306c49c8c466041d2c752bd7aaf209479c66fc75b5efae4541b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca664c152becacc6a23b694d954ade09de98336d288ef5afc9028fd118d1461f 0.600000000000 1645452 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": 1159823, "vin": [ { "gen": { "height": 1159813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca664c152becacc6a23b694d954ade09de98336d288ef5afc9028fd118d1461f" } } ], "extra": [ 1, 12, 81, 21, 235, 14, 106, 227, 6, 196, 156, 140, 70, 96, 65, 210, 199, 82, 189, 122, 175, 32, 148, 121, 198, 111, 199, 91, 94, 250, 228, 84, 27, 2, 17, 0, 0, 0, 1, 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