Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a044b69aec4ff9b538d23cf7b4f1d818e4aa3b6bc14d97266ff9e161c34c0616

Tx prefix hash: d0a4130ddacda80f80fe64a6f4507c21ef273cc4f754eec397c90d967e0c86fc
Tx public key: 6ead504e3feed5c53ad737b57664cf4f3678035a28423fac9c3f9c6cd83babf2
Timestamp: 1728857662 Timestamp [UCT]: 2024-10-13 22:14:22 Age [y:d:h:m:s]: 00:160:22:38:07
Block: 1130992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114797 RingCT/type: yes/0
Extra: 016ead504e3feed5c53ad737b57664cf4f3678035a28423fac9c3f9c6cd83babf202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8debe9cd2a287d2e162144fde361da17baae2dc7d833dd4bd3eeca8fea7288d7 0.600000000000 1613873 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": 1131002, "vin": [ { "gen": { "height": 1130992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8debe9cd2a287d2e162144fde361da17baae2dc7d833dd4bd3eeca8fea7288d7" } } ], "extra": [ 1, 110, 173, 80, 78, 63, 238, 213, 197, 58, 215, 55, 181, 118, 100, 207, 79, 54, 120, 3, 90, 40, 66, 63, 172, 156, 63, 156, 108, 216, 59, 171, 242, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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