Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6064bf95bbfe42c337f54a067d67f7fe4be2d12c935291797beaadcec04a2570

Tx prefix hash: eb3a2325a14f23cb04abc404d1ddf367f2b5c9c534503e8cff56aa963371c960
Tx public key: 01ef6827fc1781eb173a0b13f87fbc4b81419bb14d6e71cf8e6ed5417d499f46
Timestamp: 1725221004 Timestamp [UCT]: 2024-09-01 20:03:24 Age [y:d:h:m:s]: 01:059:06:01:33
Block: 1100847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300776 RingCT/type: yes/0
Extra: 0101ef6827fc1781eb173a0b13f87fbc4b81419bb14d6e71cf8e6ed5417d499f46021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09e8e15b0df64ab53b72a657cfa7a31b6cc3677cc9eac025c5fe620e17596927 0.600000000000 1576828 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": 1100857, "vin": [ { "gen": { "height": 1100847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09e8e15b0df64ab53b72a657cfa7a31b6cc3677cc9eac025c5fe620e17596927" } } ], "extra": [ 1, 1, 239, 104, 39, 252, 23, 129, 235, 23, 58, 11, 19, 248, 127, 188, 75, 129, 65, 155, 177, 77, 110, 113, 207, 142, 110, 213, 65, 125, 73, 159, 70, 2, 17, 0, 0, 0, 8, 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