Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b045f481eae5a9d3f2a78fea36eb1788386d81e475cdf435345f32095d8d4e41

Tx prefix hash: 11a4e4d370a224c981a244b4b3679069a2b2a6b4b709ac5c02d974a3fb7785ef
Tx public key: 5dae867f0b98abc3ae2e84fddfd4bf503a30eb32c8a3b0f40a3be145d8fcdca9
Timestamp: 1723496720 Timestamp [UCT]: 2024-08-12 21:05:20 Age [y:d:h:m:s]: 00:280:03:45:50
Block: 1086539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200152 RingCT/type: yes/0
Extra: 015dae867f0b98abc3ae2e84fddfd4bf503a30eb32c8a3b0f40a3be145d8fcdca9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa1d4e9c7c4a9cf822b1e300cf1622c77cfeb19df0e8987e38bfa1fce16747cb 0.600000000000 1561136 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": 1086549, "vin": [ { "gen": { "height": 1086539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa1d4e9c7c4a9cf822b1e300cf1622c77cfeb19df0e8987e38bfa1fce16747cb" } } ], "extra": [ 1, 93, 174, 134, 127, 11, 152, 171, 195, 174, 46, 132, 253, 223, 212, 191, 80, 58, 48, 235, 50, 200, 163, 176, 244, 10, 59, 225, 69, 216, 252, 220, 169, 2, 17, 0, 0, 0, 5, 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