Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12dec9065c2fc4d3cfffe40884725600e34f1ce3be2e89a4f9636f35961c52e

Tx prefix hash: b6fa7ee205265b0b5d9925d720e7aaad4e4d12df22d80130339877d98bf7a4dd
Tx public key: e5c018ae1b4918c8e47b459284f4b56a04b56ed2c96af5416e5f0511b917697c
Timestamp: 1728158873 Timestamp [UCT]: 2024-10-05 20:07:53 Age [y:d:h:m:s]: 01:003:08:42:33
Block: 1125197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260749 RingCT/type: yes/0
Extra: 01e5c018ae1b4918c8e47b459284f4b56a04b56ed2c96af5416e5f0511b917697c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 629da7d83af83eb80be5894e2b8ee976a701e7a60b52cdd0c232857fcbfb90c1 0.600000000000 1607874 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": 1125207, "vin": [ { "gen": { "height": 1125197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "629da7d83af83eb80be5894e2b8ee976a701e7a60b52cdd0c232857fcbfb90c1" } } ], "extra": [ 1, 229, 192, 24, 174, 27, 73, 24, 200, 228, 123, 69, 146, 132, 244, 181, 106, 4, 181, 110, 210, 201, 106, 245, 65, 110, 95, 5, 17, 185, 23, 105, 124, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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