Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19c212a6f0ef99c5145b492030e7df00a0a27a5e4fbd76beae8579009d81e43b

Tx prefix hash: e787a4e48e22c04755918b609cdbde4f25219d718b8457f6c8d781c154232456
Tx public key: e7d3a6532f55882f6dc17d9869631a06c2bfe38bffac26b6f50686d831d2c055
Timestamp: 1720946439 Timestamp [UCT]: 2024-07-14 08:40:39 Age [y:d:h:m:s]: 01:120:14:51:33
Block: 1065415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344710 RingCT/type: yes/0
Extra: 01e7d3a6532f55882f6dc17d9869631a06c2bfe38bffac26b6f50686d831d2c055021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d9a8af72fd0a0deb228253899567a164dc3771332146f91f85d64c94e0f30a 0.600000000000 1535960 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": 1065425, "vin": [ { "gen": { "height": 1065415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d9a8af72fd0a0deb228253899567a164dc3771332146f91f85d64c94e0f30a" } } ], "extra": [ 1, 231, 211, 166, 83, 47, 85, 136, 47, 109, 193, 125, 152, 105, 99, 26, 6, 194, 191, 227, 139, 255, 172, 38, 182, 245, 6, 134, 216, 49, 210, 192, 85, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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