Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41aa71fa20a97393ed0208ed012cee2e9f36ff25bf0f91fb9a9da4e1bc68648

Tx prefix hash: f597681f306b041b067c289d59a3d771ca87efb2d22afa41fe9e475c59d5dee5
Tx public key: 1f5f91451573c1131a718d5adc4186729ef129eb5d93503f2c6310c6e2f62650
Timestamp: 1735179342 Timestamp [UCT]: 2024-12-26 02:15:42 Age [y:d:h:m:s]: 01:031:01:49:53
Block: 1183280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280503 RingCT/type: yes/0
Extra: 011f5f91451573c1131a718d5adc4186729ef129eb5d93503f2c6310c6e2f62650021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da43a8eab7300b2ef74c63b0499a2b688fed5e526c899590e5cfcf1d8554c360 0.600000000000 1669721 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": 1183290, "vin": [ { "gen": { "height": 1183280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da43a8eab7300b2ef74c63b0499a2b688fed5e526c899590e5cfcf1d8554c360" } } ], "extra": [ 1, 31, 95, 145, 69, 21, 115, 193, 19, 26, 113, 141, 90, 220, 65, 134, 114, 158, 241, 41, 235, 93, 147, 80, 63, 44, 99, 16, 198, 226, 246, 38, 80, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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