Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b05b4a1f54cdcf0fde01e0daf418d2e4173297e38413b7bee4fc4566586e68ed

Tx prefix hash: 732cf2a74e80762b528b22415821f95db24b338c64d9787a5725a409ae8180e5
Tx public key: 8acc4e078e6295b40e893d0ee5d91ecc0806806626b718a3ce35e270b5171258
Timestamp: 1732138299 Timestamp [UCT]: 2024-11-20 21:31:39 Age [y:d:h:m:s]: 00:007:12:51:50
Block: 1158090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5399 RingCT/type: yes/0
Extra: 018acc4e078e6295b40e893d0ee5d91ecc0806806626b718a3ce35e270b51712580211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1941509e5c9cec0f107dfd28637c747d79414804780e91e5ffd3dc15d6f58af 0.600000000000 1643719 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": 1158100, "vin": [ { "gen": { "height": 1158090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1941509e5c9cec0f107dfd28637c747d79414804780e91e5ffd3dc15d6f58af" } } ], "extra": [ 1, 138, 204, 78, 7, 142, 98, 149, 180, 14, 137, 61, 14, 229, 217, 30, 204, 8, 6, 128, 102, 38, 183, 24, 163, 206, 53, 226, 112, 181, 23, 18, 88, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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