Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3621ef45d2c5e25bc226076d00d462596f8b090adfc6a8e5f1871ad26d53c0ee

Tx prefix hash: d52bc836a62e1c6121236fac4a0e052d2c1e95dd8c7f9045758021ee9213e2e7
Tx public key: dc6a15946ece5f58b1d86f630ccea9fa48bef9b1e0f2ee2d031e08eae1c44260
Timestamp: 1710690228 Timestamp [UCT]: 2024-03-17 15:43:48 Age [y:d:h:m:s]: 01:094:01:50:54
Block: 980390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328123 RingCT/type: yes/0
Extra: 01dc6a15946ece5f58b1d86f630ccea9fa48bef9b1e0f2ee2d031e08eae1c442600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f675d885ad1f614f675ab1e1079d69cf0a686f366fb28f1bba4c62fb8e1d2c1 0.600000000000 1440455 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": 980400, "vin": [ { "gen": { "height": 980390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f675d885ad1f614f675ab1e1079d69cf0a686f366fb28f1bba4c62fb8e1d2c1" } } ], "extra": [ 1, 220, 106, 21, 148, 110, 206, 95, 88, 177, 216, 111, 99, 12, 206, 169, 250, 72, 190, 249, 177, 224, 242, 238, 45, 3, 30, 8, 234, 225, 196, 66, 96, 2, 17, 0, 0, 0, 2, 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