Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3223634d992e41af75f87003c6fdd8c36958ffa3f96a9c07264590f23bd3c8

Tx prefix hash: 3c3f885a6242de5e5222b12b88e0964cdf6921a94b9da425cbfe031ed4633f1f
Tx public key: a6ae2c3fef9b20c11146d53b102f726dd55d6ab1afc274cfa4017308e0a27797
Timestamp: 1750273241 Timestamp [UCT]: 2025-06-18 19:00:41 Age [y:d:h:m:s]: 00:155:18:19:28
Block: 1307828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109137 RingCT/type: yes/0
Extra: 01a6ae2c3fef9b20c11146d53b102f726dd55d6ab1afc274cfa4017308e0a2779702110000000ebf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7983cbeab86305bbc4d92e7ce6074088b3eabb721d2f9547e4792785c9a6b28a 0.600000000000 1795439 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": 1307838, "vin": [ { "gen": { "height": 1307828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7983cbeab86305bbc4d92e7ce6074088b3eabb721d2f9547e4792785c9a6b28a" } } ], "extra": [ 1, 166, 174, 44, 63, 239, 155, 32, 193, 17, 70, 213, 59, 16, 47, 114, 109, 213, 93, 106, 177, 175, 194, 116, 207, 164, 1, 115, 8, 224, 162, 119, 151, 2, 17, 0, 0, 0, 14, 191, 81, 178, 162, 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